Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remote.nextstrain_dot_org: Include an explicit origin in error messages #391

Merged
merged 1 commit into from
Aug 27, 2024

Conversation

tsibley
Copy link
Member

@tsibley tsibley commented Aug 20, 2024

Otherwise, for remote origins other than the default of nextstrain.org, the error messages suggest incorrect/misleading possible solutions in the form of commands to run.

Motivated by @jameshadfield's comments in Slack.¹

¹ https://bedfordlab.slack.com/archives/C01LCTT7JNN/p1723760025178909?thread_ts=1723701856.612259&cid=C01LCTT7JNN

Checklist

  • Checks pass

Otherwise, for remote origins other than the default of nextstrain.org,
the error messages suggest incorrect/misleading possible solutions in
the form of commands to run.

Motivated by @jameshadfield's comments in Slack.¹

¹ <https://bedfordlab.slack.com/archives/C01LCTT7JNN/p1723760025178909?thread_ts=1723701856.612259&cid=C01LCTT7JNN>
@tsibley tsibley force-pushed the trs/remote/origin-in-error-messages branch from 94a1f81 to 740b0bf Compare August 20, 2024 21:51
@tsibley tsibley merged commit 0f35a6f into master Aug 27, 2024
42 checks passed
@tsibley tsibley deleted the trs/remote/origin-in-error-messages branch August 27, 2024 18:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants